Rename skill: microsoft-build-cli to microsoft-build#9
Conversation
Per the Agent Skills spec (agentskills.io/specification), the skill name must match the parent directory name. The folder is already skills/microsoft-build/, so the name should be microsoft-build. Also: users ask 'What's new at Build for my project?' — the agent activates on 'build' in the description, not 'cli'. The -cli suffix adds no discovery value and violates the spec. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
mikekinsman
left a comment
mikekinsman
left a comment
There was a problem hiding this comment.
reviewed internally and approved
|
One more README suggestion for the "How It Works" section: The CLI uses text-based search (MiniSearch) with field boosting, not semantic ranking. For broad topics like "Foundry" that match 50+ sessions, the default limit returns 10 results — which may not include the most relevant ones for a specific project. The agent compensates by running multiple searches from different angles and applying its own relevance ranking, but it is working from a subset. Worth adding a line to the README like:
|
2 participants
One-line change in SKILL.md frontmatter.
Why:
The Agent Skills spec (agentskills.io/specification) requires the name field to match the parent directory name. The folder is skills/microsoft-build/, so the name must be microsoft-build.
Users don't ask for a CLI — they ask 'What is new at Build for my project?' The agent activates on 'build' in the description, not 'cli' in the name. The -cli suffix adds no discovery value.
What changes: name: microsoft-build-cli becomes name: microsoft-build